chore(deps): update astro monorepo (major) #1868
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.2.2 || ^2.0.0 || ^3.0.0->^1.2.2 || ^2.0.0 || ^3.0.0 || ^4.0.03.6.3->4.4.2^1.0.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0->^1.0.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.06.0.2->7.2.2^1.2.2 || ^2.0.0 || ^3.0.0 || ^4.0.0->^1.2.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.04.5.3->5.1.3^3.0.0 || ^4.0.0->^3.0.0 || ^4.0.0 || ^5.0.04.16.15->5.16.0Release Notes
withastro/astro (@astrojs/react)
v4.4.2Compare Source
Patch Changes
#14715
3d55c5dThanks @ascorbic! - Adds support for client hydration ingetContainerRenderer()The
getContainerRenderer()function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually callcontainer.addClientRenderer()with the appropriate client renderer entrypoint.See the
container-with-vitestdemo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.v4.4.1Compare Source
Patch Changes
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVEv4.4.0Compare Source
Minor Changes
#14386
f75f446Thanks @yanthomasdev! - Stabilizes the formerly experimentalgetActionState()andwithState()functions introduced in@astrojs/reactv3.4.0 used to integrate Astro Actions with React 19'suseActionState()hook.This example calls a
likeaction that accepts apostIdand returns the number of likes. Pass this action to thewithState()function to apply progressive enhancement info, and apply touseActionState()to track the result:You can also access the state stored by
useActionState()from your action handler. CallgetActionState()with the API context, and optionally apply a type to the result:If you were previously using this experimental feature, you will need to update your code to use the new stable exports:
// src/components/Form.jsx import { actions } from 'astro:actions'; -import { experimental_withState } from '@​astrojs/react/actions'; +import { withState } from '@​astrojs/react/actions'; import { useActionState } from "react";// src/actions/index.ts import { defineAction, type SafeResult } from 'astro:actions'; import { z } from 'astro:schema'; -import { experimental_getActionState } from '@​astrojs/react/actions'; +import { getActionState } from '@​astrojs/react/actions';v4.3.1Compare Source
Patch Changes
c24a8f4Thanks @jsparkdev! - Updatesviteversion to fix CVEv4.3.0Compare Source
Minor Changes
#13809
3c3b492Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.
v4.2.7Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv4.2.6Compare Source
Patch Changes
e1cd1aeThanks @florian-lefebvre! - Fixes SSR renderer typev4.2.5Compare Source
Patch Changes
a19a185Thanks @florian-lefebvre! - Improves type-safety of renderersv4.2.4Compare Source
Patch Changes
#13596
3752519Thanks @jsparkdev! - update vite to latest version to fix CVE#13547
360cb91Thanks @jsparkdev! - Updates vite to the latest versionv4.2.3Compare Source
Patch Changes
ff9d69eThanks @jsparkdev! - updateviteto the latest versionv4.2.2Compare Source
Patch Changes
a98ae5bThanks @ematipico! - Updates the dependencyviteto the latest.v4.2.1Compare Source
Patch Changes
80926faThanks @ematipico! - Updatesesbuildandviteto the latest to avoid false positives audits warnings caused byesbuild.v4.2.0Compare Source
Minor Changes
#13036
3c90d8fThanks @artmsilva! - Adds experimental support for disabling streamingThis is useful to support libraries that are not compatible with streaming such as some CSS-in-JS libraries. To disable streaming for all React components in your project, set
experimentalDisableStreaming: trueas a configuration option for@astrojs/react:// astro.config.mjs import { defineConfig } from 'astro/config'; import react from '@​astrojs/react'; export default defineConfig({ integrations: [ react({ + experimentalDisableStreaming: true, }), ], });v4.1.6Compare Source
Patch Changes
#12996
80c6801Thanks @bluwy! - Removes hardcodedssr.external: ['react-dom/server', 'react-dom/client']config that causes issues with adapters that bundle all dependencies (e.g. Cloudflare). These externals should already be inferred by default by Vite when deploying to a server environment.#13011
cf30880Thanks @ascorbic! - Upgrades Vitev4.1.5Compare Source
Patch Changes
ea603aeThanks @louisescher! - Adds a warning message when multiple JSX-based UI frameworks are being used without either theincludeorexcludeproperty being set on the integration.v4.1.4Compare Source
Patch Changes
c7642fbThanks @bluwy! - Removes react-specific entrypoints inoptimizeDeps.includeand rely on@vitejs/plugin-reactto addv4.1.3Compare Source
Patch Changes
51ab7b5Thanks @bluwy! - Supports checking for React 19 componentsv4.1.2Compare Source
Patch Changes
739dbfbThanks @ascorbic! - Upgrades Vite to pin esbuildv4.1.1Compare Source
Patch Changes
391df0eThanks @matthewp! - Preoptimize React compiler runtimev4.1.0Compare Source
Minor Changes
97c9265Thanks @bskimball! - Add React 19 stable to peer dependenciesv4.0.0Compare Source
Major Changes
9f44019Thanks @bluwy! - Updates Vite dependency to v6 to match Astro v5Minor Changes
#12539
827093eThanks @bluwy! - Drops node 21 support#12510
14feaf3Thanks @bholmesdev! - Changes the generated URL query param from_astroActionto_actionwhen submitting a form using Actions. This avoids leaking the framework name into the URL bar, which may be considered a security issue.withastro/astro (@astrojs/svelte)
v7.2.2Compare Source
Patch Changes
#14715
3d55c5dThanks @ascorbic! - Adds support for client hydration ingetContainerRenderer()The
getContainerRenderer()function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually callcontainer.addClientRenderer()with the appropriate client renderer entrypoint.See the
container-with-vitestdemo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.v7.2.1Compare Source
Patch Changes
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVEv7.2.0Compare Source
Minor Changes
#14430
78011baThanks @ascorbic! - Adds support for async server renderingSvelte 5.36 added experimental support for async rendering. This allows you to use
awaitin your components in several new places. This worked out of the box with client-rendered components, but server-rendered components needed some extra help. This update adds support for async server rendering in Svelte components used in Astro.To use async rendering, you must enable it in your Svelte config:
Then you can use
awaitin your components:See the Svelte docs for more information on using
awaitin Svelte components, including inside$derivedblocks and directly in markup.Patch Changes
9cc8f21Thanks @ascorbic! - Fixes a bug that prevented Svelte 5.39.1+ components rendering when multiple frameworks were presentv7.1.1Compare Source
Patch Changes
c24a8f4Thanks @jsparkdev! - Updatesviteversion to fix CVEv7.1.0Compare Source
Minor Changes
#13809
3c3b492Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.
v7.0.13Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv7.0.12Compare Source
Patch Changes
e1cd1aeThanks @florian-lefebvre! - Fixes SSR renderer typev7.0.11Compare Source
Patch Changes
a19a185Thanks @florian-lefebvre! - Improves type-safety of renderersv7.0.10Compare Source
Patch Changes
#13596
3752519Thanks @jsparkdev! - update vite to latest version to fix CVE#13547
360cb91Thanks @jsparkdev! - Updates vite to the latest versionv7.0.9Compare Source
Patch Changes
ff9d69eThanks @jsparkdev! - updateviteto the latest versionv7.0.8Compare Source
Patch Changes
a98ae5bThanks @ematipico! - Updates the dependencyviteto the latest.v7.0.7Compare Source
Patch Changes
ecadb6bThanks @ascorbic! - Hides fallback content when renderingclient:onlyislandv7.0.6Compare Source
Patch Changes
a05e6abThanks @Hugos68! - Fixes a case where$props.id()would not be unique across multiple islandsv7.0.5Compare Source
Patch Changes
80926faThanks @ematipico! - Updatesesbuildandviteto the latest to avoid false positives audits warnings caused byesbuild.v7.0.4Compare Source
Patch Changes
cf30880Thanks @ascorbic! - Upgrades Vitev7.0.3Compare Source
Patch Changes
8809b85Thanks @aminevg! - Fixes an issue where TypeScript couldn't infer the correct types of theserver.mjsfilev7.0.2Compare Source
Patch Changes
739dbfbThanks @ascorbic! - Upgrades Vite to pin esbuildv7.0.1Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv7.0.0Compare Source
Major Changes
#12060
cb5d3aeThanks @Princesseuh! - Updates peer dependency range to support Astro 5#12524
9f44019Thanks @bluwy! - Updates@sveltejs/vite-plugin-svelteto v5 to handle Vite 6#12524
9f44019Thanks @bluwy! - Updates Vite dependency to v6 to match Astro v5Minor Changes
827093eThanks @bluwy! - Drops node 21 supportPatch Changes
#12102
dcc1e89Thanks @hermit99! - Fixes an Reference Error that occurred during client transitions#12551
b21a075Thanks @ematipico! - New release to include changes from 5.7.3withastro/astro (@astrojs/vue)
v5.1.3Compare Source
Patch Changes
#14715
3d55c5dThanks @ascorbic! - Adds support for client hydration ingetContainerRenderer()The
getContainerRenderer()function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually callcontainer.addClientRenderer()with the appropriate client renderer entrypoint.See the
container-with-vitestdemo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.v5.1.2Compare Source
Patch Changes
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVEv5.1.1Compare Source
Patch Changes
c24a8f4Thanks @jsparkdev! - Updatesviteversion to fix CVEv5.1.0Compare Source
Minor Changes
#13809
3c3b492Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.
v5.0.13Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv5.0.12Compare Source
Patch Changes
e1cd1aeThanks @florian-lefebvre! - Fixes SSR renderer typev5.0.11Compare Source
Patch Changes
a19a185Thanks @florian-lefebvre! - Improves type-safety of renderersv5.0.10Compare Source
Patch Changes
#13596
3752519Thanks @jsparkdev! - update vite to latest version to fix CVE#13547
360cb91Thanks @jsparkdev! - Updates vite to the latest versionv5.0.9Compare Source
Patch Changes
ff9d69eThanks @jsparkdev! - updateviteto the latest versionv5.0.8Compare Source
Patch Changes
a98ae5bThanks @ematipico! - Updates the dependencyviteto the latest.v5.0.7Compare Source
Patch Changes
3842ce5Thanks @florian-lefebvre! - Fixes a case where the compiler could not be resolved automaticallyv5.0.6Compare Source
Patch Changes
cf30880Thanks @ascorbic! - Upgrades Vitev5.0.5Compare Source
Patch Changes
ea603aeThanks @louisescher! - Adds a warning message when multiple JSX-based UI frameworks are being used without either theincludeorexcludeproperty being set on the integration.v5.0.4Compare Source
Patch Changes
8809b85Thanks @aminevg! - Fixes an issue where TypeScript couldn't infer the correct types of theserver.mjsfilev5.0.3Compare Source
Patch Changes
739dbfbThanks @ascorbic! - Upgrades Vite to pin esbuildv5.0.2Compare Source
Patch Changes
7dc2fcaThanks @yoyo837! - fix vite peer dependency issue for vue integrationv5.0.1Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv5.0.0Compare Source
Major Changes
#12060
cb5d3aeThanks @Princesseuh! - Updates peer dependency range to support Astro 5#12524
9f44019Thanks @bluwy! - Updates Vite dependency to v6 to match Astro v5Minor Changes
827093eThanks @bluwy! - Drops node 21 supportPatch Changes
81b0bf5Thanks @ematipico! - New release to include changes from 4.5.2withastro/astro (astro)
v5.16.0Compare Source
Minor Changes
#13880
1a2ed01Thanks @azat-io! - Adds experimental SVGO optimization support for SVG assetsAstro now supports automatic SVG optimization using SVGO during build time. This experimental feature helps reduce SVG file sizes while maintaining visual quality, improving your site's performance.
To enable SVG optimization with default settings, add the following to your
astro.config.mjs:To customize optimization, pass a SVGO configuration object:
For more information on enabling and using this feature in your project, see the experimental SVG optimization docs.
#14810
2e845feThanks @ascorbic! - Adds a hint for code agents to use the--yesflag to skip prompts when runningastro add#14698
f42ff9bThanks @mauriciabad! - Adds theActionInputSchemautility type to automatically infer the TypeScript type of an action's input based on its Zod schemaFor example, this type can be used to retrieve the input type of a form action:
#14574
4356485Thanks @jacobdalamb! - Adds new CLI shortcuts available when runningastro preview:o+enter: open the site in your browserq+enter: quit the previewh+enter: print all available shortcutsPatch Changes
#14813
e1dd377Thanks @ematipico! - Removespicocolorsas dependency in favor of the forkpiccolore.#14609
d774306Thanks @florian-lefebvre! - Improvesastro info#14796
c29a785Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyUpdates the default
subsetsto["latin"]Subsets have been a common source of confusion: they caused a lot of files to be downloaded by default. You now have to manually pick extra subsets.
Review your Astro config and update subsets if you need, for example if you need greek characters:
import { defineConfig, fontProviders } from "astro/config" export default defineConfig({ experimental: { fonts: [{ name: "Roboto", cssVariable: "--font-roboto", provider: fontProviders.google(), + subsets: ["latin", "greek"] }] } })v5.15.9Compare Source
Patch Changes
#14786
758a891Thanks @mef! - Add handling of invalid encrypted props and slots in server islands.#14783
504958fThanks @florian-lefebvre! - Improves the experimental Fonts API build log to show the number of downloaded files. This can help spotting excessive downloading because of misconfiguration#14791
9e9c528Thanks @Princesseuh! - Changes the remote protocol checks for images to require explicit authorization in order to use data URIs.In order to allow data URIs for remote images, you will need to update your `a
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.